…tual info to warning

In the previous implementation (PR ChrisTitusTech#127), there was an edge case where a powershell update check will take place and a profile update check might not
due to floating point vs int values (.Date vs without (L84 vs L125 in aforementioned PR)).
Commonize the checks since no situation exists where one runs but the other does not.

Add better dev-centered warning message since the previous warning was made to address the fact the profile has transitioned from update checks every launch
to a periodic check, now that users are aware of it, we can notify them when the next update will occur rather than the fact it was just skipped. (Issue ChrisTitusTech#130)

Signed-off-by: Anirudh Gupta <anirudhgupta109@gmail.com>